Systems and methods for name pronunciation

ABSTRACT

Systems and methods are provided for associating a phonetic pronunciation with a name by receiving the name, mapping the name to a plurality of monosyllabic components that are combinable to construct the phonetic pronunciation of the name, receiving a user input to select one or more of the plurality, and combining the selected one or more of the plurality of monosyllabic components to construct the phonetic pronunciation of the name.

FIELD

This application relates to recognizing and synthesizing speech and,more particularly, to recognizing and synthesizing pronunciations ofnames.

BACKGROUND

Name recognition is a particularly difficult aspect of speechrecognition. Names can include names of people, businesses, and otherentities. The distribution of names has a long tail. Furthermore, theway names are pronounced can be subjective and dependent on the name'sorigin. There can be a few names that are very common, but an order ofmagnitude more names that are very rare. For a speech recognition systemto recognize names, a linguist is typically needed to transcribe allpossible pronunciations in a phonetic alphabet supported by the localeor language in which the speech recognition system is deployed. Mostexisting speech recognition and synthesis system have up to hundreds orthousands of names, while there are likely millions of actual uniquenames in use today.

Current speech recognition systems typically model name recognition tosupport tasks such as phone dialing, search and query, reminders, andevents scheduling based on a named entry in a contact application of auser device. To recognize or synthesize a name, current systems oftenuse a dictionary or a lexicon. These contain a mapping of the names totheir possible pronunciations. However, if a name has not been modeledin the speech lexicon, the system must guess the pronunciation. For thepurpose of speech synthesis, the system may also need to guess thestress on individual syllables comprised in the name.

For names not modeled explicitly in the lexicon, speech recognitionsystems typically depend on a pronunciation guesser that usessophisticated letter-to-sound rules. However, because certain phoneticunits are particular to a specific language, the same name may bepronounced differently by different users. Thus, existing systems arenot capable of building an adequate pronunciation guesser that modelsthe pronunciation of names from different languages and cultures. Inmany cases, a foreign name pronunciation may not be guessed properlyunless explicit rules are represented within the guesser.

SUMMARY

The application, in various implementations, provides systems, methodsand devices that provide a user interface to efficiently andconveniently configure the phonetic pronunciation of names.

In one aspect a system generates a phonetic pronunciation of a namebased on user selection of the name's monosyllabic components. Thesystem may associate a phonetic pronunciation with a name. The systemmay include a user interface arranged to receive the name. The systemmay also include a processor arranged to map the name to a plurality ofmonosyllabic components that are combinable to construct the phoneticpronunciation of the name. The user interface may also be arranged toreceive a user input to select one or more of the plurality ofmonosyllabic components. Furthermore, the processor may be arranged tocombine the selected one or more of the plurality of monosyllabiccomponents to construct the phonetic pronunciation of the name.

In one configuration, the user interface is arranged to provide thephonetic pronunciation to the user. The user interface may be arrangedto receive a second user input to select or reject the phoneticpronunciation. The user interface may also be arranged to display afirst portion of the plurality of monosyllabic components to the user.The user interface may further be arranged to display a second portionof the monosyllabic components in response to a user selection of one ofthe first portion of the plurality of monosyllabic components.

The processor may be arranged to receive the name from a contact list ofa contact application and/or other application associated with the user.The name may be in text format. The processor may be arranged to query adata store and/or database that includes one or more of the monosyllabiccomponents associated with the name. The monosyllabic components mayinclude components associated with one or more languages, cultures,and/or locales. The construction of the phonetic pronunciation of thename may include generating an audio file.

In another aspect, a system for determining usage information associatedwith the phonetic pronunciation of a name may include a server arrangedto receive one or more contact names. The system may include a datastore arranged to store one or more phonetic pronunciations associatedwith the one or more names. The server may be arranged to receive anindication of the one or more phonetic pronunciations associated withthe one or more names from one or more user devices and determine usagedata associated with the one or more phonetic pronunciations associatedwith the one or more names.

The indication may include the one or more phonetic pronunciations. Theindication may include a selection of the one or more phoneticpronunciations from the one or more user devices. The usage data mayinclude an amount of instances that the indication is received during aperiod of time. The server may be arranged to provide at least one ofthe phonetic pronunciations associated with the name to a first userdevice based on the usage data.

In another aspect, a system may include and/or be provided with aplurality of pronunciation guessers where each of the pronunciationguessers are associated with a particular phonetic alphabet of alanguage or locale. For example, the phonetic alphabets may be, withoutlimitation, English, French, German, Spanish, and Italian. A processordetermines a language or locale associated with a user and associates afirst phonetic alphabet (e.g., English) with the language or localeassociated with the user. The determination of language and/or localemay be via manufacturer input, service provider input, user input,detection of the geographic area associated with the location of thesystem, analysis of the types of names and/or other words input by auser, and the like.

Each of the pronunciation guessers may receive a representation of thename. The representation may be orthographic. Orthography may generallyrefer to the spelling of a word. The orthographic representation maydefine phonemes and/or symbols (e.g., graphemes and/or dialect) of alanguage associated with the representation of a word and/or name. Eachof the plurality of pronunciation guessers may then guess a phoneticpronunciation of one or more components of the name. Then, a phoneticmapper may map the phonetic pronunciation of the one or more componentsof the name guessed by each of the plurality of pronunciation guessersto the first phonetic alphabet to generate a list of guessedpronunciations. A speech recognizer may receive an audio pronunciationof the name and then select a combination of components from the list ofguessed pronunciations that, when pronounced, substantially and/or bestmatch the audio pronunciation of the name.

Each of the one or more components of the name may include at least oneof a sound unit, a phoneme, a mono-syllabic component, a mono-syllabiccomponent with a particular type of stress, and portion of a word. Theprocessor 102 may identify the language or locale associated with theuser. The number of pronunciation guessers may be determined based onthe language or locale associated with the user. The type of each of theplurality of pronunciation guessers may be determined based on thelanguage or locale associated with the user. The type of pronunciationguesser may include the type of language or locale associated with thepronunciation guesser.

Various advantages and applications for using a name pronunciationsystem and interface in accordance with principles of the presentdisclosure are discussed in more detail below.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other features of the present application, its nature andvarious advantages will become more apparent upon consideration of thefollowing detailed description, taken in conjunction with theaccompanying drawings, in which like reference characters refer to likeparts throughout, and in which:

FIG. 1 is a diagram including components of a user-driven namepronunciation system;

FIG. 2 is a diagram of a computer processing environment includingvarious functions, applications and/or routines running within auser-driven pronunciation system;

FIG. 3 is a diagram of a network including a user-driven namepronunciation system;

FIG. 4 is a flow diagram of a process for generating a pronunciation ofa name from a contact list or user input;

FIG. 5 is a display of a name including its monosyllabic components;

FIG. 6 is a display of another name including its monosyllabiccomponents;

FIG. 7 is a display of yet another name including its monosyllabiccomponents;

FIG. 8 is a diagram of a system for determining phonetic pronunciationsof a name.

FIG. 9 is a flow diagram of a process for generating a phoneticpronunciation of a name

FIG. 10 is a flow diagram of another process for generating a phoneticpronunciation of a name based on user selection of the name'smonosyllabic components; and

FIG. 11 is a flow diagram of a process for determining usage informationassociated with the phonetic pronunciation of a name.

DETAILED DESCRIPTION OF THE DISCLOSURE

The application, in various implementations, provides systems, methodsand devices that provide a user interface to efficiently andconveniently configure the phonetic pronunciation of names. In certainconfigurations, the interface uses a processor that implements anapplication for mapping an arbitrary name from a user's contact to aplurality of monosyllabic names to construct the correct pronunciationof the name. The name may first be syllabified into multiplemono-syllabic words that are easily pronounced by a user in a languageof transcribed intent. A syllable may be considered a single element ofspoken language that includes a single uninterrupted sound formed by avowel, diphthong, or syllabic consonant. The sound may be preceded by,followed, or surrounded by a single consonant or multiple consonants.

In certain configurations, an interface allows a user to enter their ownmono-syllabic words to accurately present the pronunciation of a name.The interface may present a sequence of mono-syllabic words to a userand enable the user to select various mono-syllabic words to form anoverall pronunciation of a name. In certain implementations, theinterface provides the user with audio associated with the selectedpronunciation as feedback to enable the user to refine thepronunciation.

The interface may allow a user to select one or more mono-syllabicwords, and/or select a particular sequence of mono-syllabic words, thatbest approximate the underlying pronunciation of a name in the user'slist of contacts. The interface may include a touch screen to enableefficient user selection of one or more of the mono-syllabic words. Theinterface may provide a best guess of the pronunciation to a user. Inone implementation, a refined pronunciation is transcribed into aphonetic alphabet supported by a speech recognition function andincorporated as a part of a lexicon of the user's dynamic vocabulary.

The lexicon may be used as part of a process for crowd-sourcingpronunciations based on inputs from multiple users. By gatheringpronunciation data from multiple users related to, for example, thetypes of mono-syllabic words used and how often certain mono-syllabicwords are used, the potentially significant cost of employing linguistscan be reduced or eliminated, while creating a more extensive andrelevant lexicon of phonetic names. The name pronunciation system alsoallows a user to utilize more accurately pronounced names forrecognition and synthesis for everyday tasks as opposed to relying onsubstandard pronunciation guessers. [0031] FIG. 1 is a diagram includingcomponents of a user-driven name pronunciation system 100. The system100 includes a user interface 102, a processor 104, and a data store106. The user interface 102 may include hardware, software, or acombination therefore arranged to provide an interface for one or moreusers to communicate with the system 100. The processor 104 may includeone more processors arranged to process data, functions, and/orapplications of the system 100. The data store 106 may include one morestorage devices.

In certain implementations, the user interface 102 allows a user tointeract with the system 100. For example, the user interface 102 mayinclude a user input device that can take a variety of forms, such as abutton, keypad, dial, a click wheel, microphone, and/or a touch screen.The user interface 102 may include an output device that can take avariety of forms such as, without limitation, a display, a speaker, atransducer, headphones, and/or a vibration generator. In certainimplementations, the user interface 102 is arranged to receive spokeninputs and/or commands from a user. The user interface 102 may outputaudio information via one or more speakers and/or headphones to a user.

In certain implementations, the processor 104 includes one or moreprocessors arranged within a user device. In other implementations, theprocessor 104 may include multiple processors among multiple devices.Further details regarding such an implementation are discussed withrespect to FIG. 3 later herein. Processor 104 may control the operationof various functions such as described later herein with respect to FIG.2, and other circuitry included in system 100. Processor 104 may drive adisplay of user interface 102 and may receive user inputs from the userinterface 102. Processor 104 may receive, retrieve, and/or send dataincluding, for example, executable code to and/or from data store 106during operations of the system 100. The processor 104 may include aCoder/decoder (CODEC) processor to convert digital audio signals intoanalog signals for driving a speaker of user interface 102 to producesound including the pronunciation of names, voice, music, and other likeaudio. The CODEC may also convert audio inputs from a microphone of theuser interface 102 into digital audio signals. The processor may storedigital audio signals as data files in the data store 106. The CODEC mayinclude a video CODEC for processing digital and/or analog videosignals. In some configurations, the processor 104 includes one or morecentral processing units (CPUs) operating in one or more user devices,personal computers, and/or servers.

In certain implementations, the data store 106 may store media (e.g.,music and video files), contact information (e.g., contact names),phonetic data associated with contact names (e.g., monosyllabic words),software (e.g., for implanting functions of the system 100, preferenceinformation (e.g., media playback preferences), transaction information(e.g., information such as credit card information), connectioninformation (e.g., information that may enable a component of system 100to establish communications with another system), subscriptioninformation (e.g., information that keeps tracks of podcasts ortelevision shows or other media a user subscribes to), and any othersuitable data. Data store 106 may include one more storage mediums,including without limitation, a hard-drive, permanent memory such asROM, semi-permanent memory such as RAM, solid state memory, removablememory, CD-ROM, CD-RW, diskette, firmware, a cache, and other likedevices capable of storing electronic data. Data store 106 may include adatabase. The database may include a relational database managementsystem (RDBMS) and/or a structured query language (SQL) database, or thelike.

FIG. 2 is a diagram of a computer processing environment 200 includingvarious functions, applications, and/or routines 202-210 running withina user-driven pronunciation system such as, for example, system 100 ofFIG. 1. The computer processing environment 200 may include apronunciation guesser 202, a speech recognizer 204, a speech synthesizer206, a contact application 208, and other applications 210.

In certain implementations, the pronunciation guesser 202 models rulesfor pronouncing words such as names from their associated textspellings. The pronunciation guesser may include learning algorithmsand/or techniques such as, without limitation, hidden-markov models,decision tree classifiers, and/or other statistical models wherephonemes or sequences of phonemes may be associated with letters,sequences of letters, and/or words to produce pronunciations of names.The pronunciation guesser may utilize data and/or libraries associatedwith one or more languages to predict a pronunciation including datafrom a database within, for example, data store 106 and/or 312.

In certain implementations, the speech recognizer 204 converts spokenwords by a user to electronic text and/or data. The speech recognizer204 may be configured to recognize speech from a particular user and/orto recognize speech generally from any user. The speech recognizer 204may be utilized in conjunction with other applications 210 such as, forexample, a voice activated dialing application for initiating atelephone call (e.g., “Call Bill”). The other applications 210 mayinclude device control (e.g., “hang up”), search (e.g., “find lovesongs”), data entry (e.g., “10 Main Street”), speech-to-text processing(e.g., inputting content of an email), and any like applicationutilizing spoken user inputs. The speech recognizer 204 may utilizeanyone of a number of models including, without limitation, hiddenmarkov models (HMMs), dynamic time warping (DTW) based speechrecognition, and/or statistical speech recognition models. The speechrecognizer 204 may use context dependencies for phonemes, vocal tractlength normalization (VTLN), maximum likelihood regression (MLLR),heteroscedastic linear discriminant analysis (HLDA), Bayesian networks,Viterbi algorithms, and/or like techniques for speech recognition.

In certain implementations, the speech synthesizer 206 electronicallyproduces human speech. The speech synthesizer 206 may be implemented insoftware, hardware, or a combination thereof. In one configuration, thesynthesizer 206 converts electronic data, electronic text, and/orsymbolic linguistic representations such as phonetic transcriptions intospeech. The synthesizer 206 may generate spoken words such as names byconcatenating portions of recorded sounds from a database such as withindata store 106 and/or 312. The speech synthesizer 206 may access phones,diphones, words, mono-syllabic components of words, and/or sentences toproduce synthesized audio outputs and/or audio files. The synthesizer206 may utilize any one or more techniques to produce natural andintelligible sounds. The techniques may include, without limitation,concatenative synthesis, unit selection synthesis, diphone synthesis,mono-syllabic component synthesis, domain-specific synthesis, formatsynthesis, articulatory synthesis, hidden markov model (HMM) synthesis,and/or sinewave synthesis. The synthesizer 206 may be utilized with oneor more applications such as contact application 208 and otherapplications 210. Siri® is a type of application that uses namerecognition that is made available by Apple Inc., of Cupertino, Calif.For example, a user may speak “Find emails from Steve” or “Call Peter athome.”

In certain implementations, the contact application 208 includes one ormore contacts associated with a user that may be stored in a list and/ordatabase. Each contact may include a contact name, address, telephonenumber, electronic mail (email) address, and/or other information. Eachcontact may include a “Phonetic First Name” and/or “Phonetic Last Name”field. The contact application 208 may be a stand-alone application thatinterfaces with other applications 210. For example, another application210 may include a wireless telephone calling application. The contactapplication 210 may interface with the calling application to initiate atelephone to a selected contact from the contact application 208. Thecontact application 208 may be integrated with other applications 210.For example, the other application 210 may include an email applicationthat enables to user to send and receive emails and/or access a mailserver. The contact application 208 may be a function of the mailapplication that enables a user to store one or more contacts withassociated information such as contact name, address, telephone number,electronic mail (email) address, and/or other information. The contactapplication and/or email application may include the contact and/or mailapplications implemented, for example, on the Apple® iPhone®, iPad®, andiPod Touch® that are made available by Apple Inc., of Cupertino, Calif.

FIG. 3 is a diagram of a network including a user-driven namepronunciation system 300. The system 300 includes user devices 302, 304,and/or 306, network 308, sever 310, and/or data store 312.

The user devices 302, 304, and/or 306 may include a personal computer(PC), personal digital assistant (PDA), a portable computing device, acellular telephone, satellite telephone, cordless telephone, pager, orany other electronic device capable of implementing one or morefunctions of environment 200 of FIG. 2. The user device 302, 304, and/or306 may be integrated within the packaging of other devices orstructures such a vehicle, video game system, appliance, clothing,helmet, glasses, wearable apparel, stereo system, entertainment system,or other portable devices. Types of user devices 302, 304, and/or 306may include, for example, an Apple® iPod®, iPad®, iPhone®, iMac®,MacBook Pro®, and MacBook Air®, and the like, that are made available byApple Inc., of Cupertino, Calif. and any other devices capable ofcommunicating in a wired and/or wireless manner.

User device 302, 304, and/or 306 may synchronize with, for example, aremote computing system or server 310 to receive media and/or userpronunciation related data (using either wireless or wirelinecommunications paths). Media may include, without limitation, sound oraudio files, music, video, multi-media, and digital data, in streamingand/or discrete (e.g., files and packets) formats.

A user device 302, 304, and/or 306 may include communications circuitryfor wired and/or wireless communication (e.g., short-range and/or longrange communication). For example, the wireless communication circuitrymay be Wi-Fi™ enabling circuitry that permits wireless communicationaccording to one of the 802.11 standards. Other wireless networkprotocols standards could also be used, either in alternative to theidentified protocols or in addition to the identified protocol. Othernetwork standards may include Bluetooth, the Global System for MobileCommunications (GSM), code division multiple access (CDMA), Long TermEvolution (LTE), and/or 4G based wireless protocols.

Any suitable circuitry, device, system, or combination of these (e.g., awireless communications infrastructure including communications towersand telecommunications servers) operative to create a communicationsnetwork may be used to create network 308. Network 308 may be capable ofproviding communications using any suitable communications protocol. Insome embodiments, network 308, user devices 302, 304, and/or 206, andserver 310 may support, for example, traditional telephone lines, cabletelevision, Wi-Fi™, Ethernet, Bluetooth™, high frequency systems (e.g.,900 MHz, 2.4 GHz, and 5.6 GHz communication systems), infrared,transmission control protocol/internet protocol (“TCP/IP”) (e.g., any ofthe protocols used in each of the TCP/IP layers), hypertext transferprotocol (“HTTP”), BitTorrent™, file transfer protocol (“FTP”),real-time transport protocol (“RTP”), real-time streaming protocol(“RTSP”), secure shell protocol (“SSH”), any other communicationsprotocol, or any combination thereof.

In certain implementations, server 314 includes one or more of a LINUX,UNIX, Windows®, or MAC OS operating system. Sever 314 may be implementedon one computer device or multiple computer devices. Data store 312 mayinclude one or more disk drives, solid state memory, volatile and/ornon-volatile memory, an array of storage disks, and/or a plurality ofredundant storage elements. Sever 314 may include a virtual serverdistributed and/or copied among multiple hardware server elements.

In one implementation, a user device 302, 304, and/or 306 includes oneor more of the components 102, 104, and 106 of FIG. 1 and one or more offunctions 202, 204, 206, 208, and 210 of FIG. 2. For example, userdevice 302 may include a portable computing device operating as a standalone user pronunciation system including the all of the components 102,104, and 106 of FIG. 1 and the functions 202, 204, 206, 208, and 210 ofFIG. 2. In one configuration, user device 302 accesses data store 312periodically or at other instances to obtain user pronunciation relateddata including contact names, contact information (e.g., address, emailaddress, telephone number, and the like), and mono-syllabic componentsassociated with contact names. User device 302 may stored userpronunciation related data locally within data store 106 and/or remotelywithin data store 312.

In another implementation, a user device 302 and server 312 may operatecooperatively to implement one or more of the functions 202, 204, 206,208, and 210 of FIG. 2. In one configuration, user device 302 operatesas a client and/or terminal for server 310 that implements the functionsof environment 200 of FIG. 2. In another configuration, user device 302and server 310 both perform one or more functions of environment 200 ofFIG. 2. In yet another configuration, user device 302 performs a portionof the functions 202, 204, 206, 208, and 210 of FIG. 2, while server 310and/or data store 312 perform another portion of the functions 202, 204,206, 208, and 210 of FIG. 2.

FIG. 4 is a flow diagram of a process 400 for generating a phoneticpronunciation of a name from a contact list or user input. One or moreof the steps of process 400 may be implemented by a user-driven namepronunciation system such as the systems 100 and 300 of FIGS. 1 and 3using, for example, one or more of the functions 202, 204, 206, 208, and210 of FIG. 2.

In one implementation, a user device, such as user device 302, includesa contact application 208 including one or more contact names. The usermay access the contact application 208 to determine a phoneticpronunciation associated with the text of the stored contact name. Thecontact name may include a first name and/or last name. Certain devicessuch as the Apple® iPhone® provide phonetic first name and phonetic lastname fields for a user to manually insert a phonetic spelling todetermine how a contact name should be pronounced. Manually entry can betime consuming while not ensuring the correct pronunciation iseventually synthesized. Thus, it would be advantageous to leverage auser's familiarity with the names in their contacts and how the userintends to pronounce such names, to provide the user with a way topresent and articulate name pronunciations efficiently and conveniently.

In certain implementations, a user can select a name via a userinterface 102 in a contact application 208 or other application 210 toassign a proper phonetic pronunciation for the name. A pronunciationguesser 202 receives the name (Step 402). Alternatively or additionally,a user device such as user device 302 may include a user interface 102for receiving spoken names and/or other words. The user interface 102may include a microphone to receive a user provided name which is thenprovided to speech recognizer 204 to convert the spoken name to text. Auser may say a name such as, for example, “Philippe” which is thenconverted to electronic data and/or text. The electronic data and/ortext for “Philippe” may then be received by the pronunciation guesser202 for further processing. A received name may be 1) either an entry ina contact, for example the “Firstname” and/or “Lastname” field for acontact application 208 in a user device 302 such as, for example, aniPhone®. The received name may be a recording of a name that isassociated with a name entry in the contact application 208. Forexample, one could have an icon displayed and/or situated next to thename that allows a user to associate a pronunciation to the name.

The pronunciation guesser 202 then over-generates a set of possiblephonetic pronunciations associated with the name (Step 404). Forexample, feature 414 of FIG. 4 shows multiple possible pronunciations ofthe term “Hafs.” In one configuration, pronunciation guesser 202 mapsone or more mono-syllabic components to a name. Mapping may includegenerating, associating, and/or obtaining the one or more mono-syllabiccomponents from a database included in, for example, data store 106and/or 312. The database may include a relational database that storesone or more contact names and one or more mono-syllabic componentsand/or words associated with and/or mapped to each contact name. Incertain configurations, the pronunciation guesser 202 may map and/orgenerate possible phonetic pronunciations based on one or more localesand/or languages. For example, the pronunciation guesser 202 may haveaccess to a database in data store 106 and/or 312 that includes alexicon of phonetic pronunciations in various languages such as English,German, French, and so on. The lexicon may include mono-syllabiccomponents associated with a name in one or more languages. For example,with respect to FIG. 5, the name “Philippe” may have an Englishcomponent 508 “fill” and a French component 506 “leap.”

Next, the generated list and/or set of possible phonetic pronunciationsare provided to, for example, recognizer 204 which performs arecognition of the possible phonetic pronunciations and selects thecloset available guess of a proper phonetic translation (Step 406). Inone configuration, recognizer 204 uses constrained speech recognition.Constrained recognition may be employed based on limited resources suchas limited processing power, the need for faster recognition, theavailability of storage capacity, the size of the lexicon of phoneticpronunciations, and/or other system constraints. The recognizer 204 mayconsider factors such as location of the user in determining the closestavailable guess. For example, if the user and/or the user device 302originate and/or reside substantially within a particular geographicarea associated with a particular language or locale, the recognizer 204may consider location when selecting the closet available guess. Therecognizer 204 may also consider the user's selections of phoneticpronunciations for other names in determining a language and/or localefor selection of the closet available guess for the name.

In an alternative implementation, the generated list and/or set ofpossible phonetic pronunciations are provided to a user via userinterface 102. In one configuration, the user interface 102 presents thelist and/or set of phonetic pronunciations including a set ofmono-syllabic components and/or words.

FIG. 5 is a display 500 of a name 502 (e.g., “Philippe”) including itsmono-syllabic components 504, 506, 508, 510, 512, 514, 516, and 518. Asyllable may be considered a single element of spoken language thatincludes a single uninterrupted sound formed by a vowel, diphthong, orsyllabic consonant. The sound may be preceded by, followed, orsurrounded by a single consonant or multiple consonants. The name 502may be a first name in a contact list of a contact application 208. Thedisplay 500 may be provided via a user interface 102 of, for example, auser device 302. The display 500 may include a touch screen capable ofreceiving a user input to select one or more mono-syllabic components.In this case, the name 502 “Philippe” can include the mono-syllabiccomponents 504 “fee”, 506 “leap”, 508 “fill”, 510 “eap”, 512 “philly”,and 514 “pay.” A user may select mono-syllabic components 504 “fee” and506 “leap” to construct a phonetic pronunciation for the name 502“Philippe.”

Alternatively, the user may select the mono-syllabic components 508“fill” and 506 “eap” to construct a different phonetic pronunciation forthe name 502 “Philippe.” As a further option, the user may selectmono-syllabic components 512 “philly” and 514 “pay” to construct anotherphonetic pronunciation for the name 502 “Philippe.” In someimplementations, the display 500 includes mono-syllabic components 516and 518 as user definable fields capable of receiving a user input todefine a mono-syllabic component or word. There may be circumstanceswhere the pronunciation guesser does not provide a mono-syllabiccomponent that sufficiently pronounces a component of a name. In suchcircumstances, the user interface 102 via display 500 can receive a userinputted word via component 516 and/or 518 that provides a mono-syllabicpronunciation of a portion of a name. In some implementations, a user isable to select any combination of the components 502-518 to construct aphonetic pronunciation of o the name 502 “Philippe.”

As previously discussed, display 500 may receive mono-syllabiccomponents associated with one or more languages or locales. Bypresenting monosyllabic components associated with one or morelanguages, the user interface 102 via display 500 efficiently provides auser with a variety of possible alternative pronunciations for a portionof a name. The one or more mono-syllabic components can be generated bypronunciation guesser 202 based on one or more lexicons and/or databasesassociated with one or more languages stored within data store 106and/or 312.

In certain configurations, user interface 102 via display 500 displaysmono-syllabic components and/or other words arranged in an order and/orsequence based on a predicted user preference. For example, in FIG. 5,the mono-syllabic component 504 “fee” is displayed above component 508“fill” possibly based on a user preference for French pronunciations,based on a user locale, based on a language associated with a user,and/or based on previous types of selections of mono-syllabic componentsmade by the user. In some configurations, user interface 102 via display500 may present mono-syllabic components in a particular sequence and/ororder based on the popularity and/or frequency of use of certainmono-syllabic components among a group of users over a period of time,and/or in a particular location.

In certain implementations, the display 500 may include one or morepoly-syllabic words looked up from a dictionary in data store 106 and/or312 that can be combined with mono-syllabic words to form a phoneticpronunciation. For example, the component 620 “money” and component 512“Philly” may be considered poly-syllabic (i.e., bi-syllabic) words thatmay be present in a pre-existing dictionary that can be also be used.Thus, certain words that may not be considered legitimate mono-syllabicwords in a dictionary, but that may be constructed from legitimatemono-syllabic words, can be included and presented to a user forconstruction of a phonetic pronunciation, wherein the user may be ableto pronounce a mono-syllable reasonably based on similar context. Forexample, the word “Tim” may be a legitimate word in a dictionary,whereas the word “nim” may not be a legitimate word, but one can make areasonable guess of how it is pronounced based on the fact that theconsonant “t” has been replaced by the consonant “n”.

FIG. 6 is another example of a display 600 of another name 602“Belyamani” including its mono-syllabic components 604-626. The userinterface 102 via display 600 may display the name 602 “Belyamani” withsome or all of its mono-syllabic components 604-626. The name 602 may bea last name in a contact list of a contact application 208. In oneconfiguration, the user interface 102 receives user selections of one ormore of the mono-syllabic components 604-626 associated with portions ofthe name 602 “Belyamani.” The mono-syllabic components 604-626 may bearranged based on characteristics of the user and/or characteristics ofa group of users. The user interface 102 may include a touch screencapable of receiving user selections of one or more of the mono-syllabiccomponents. The user interface 102 may include other devices capable ofreceiving user inputs such as, without limitation, a mouse, keypad,click wheel, microphone, and so one.

In one implementation, user interface 102 via display 600 may present aportion of the mono-syllabic components while not presenting anotherportion of mono-syllabic components unless or until the other portionbecomes relevant for user selection. For example, display 600 mayinitially display only components 604 “bell”, 610 “bail”, 616 “bale”,and 622. Depending on which component a user selects, user interface 102via display 600 may then display one or more of the other components606, 608, 612, 614, 618, 620, 624, and 626. For example, if the userselects component 604 “bell,” then user interface may only showcomponents 606 “ya”, 608 “mani”, and 630 “money” while not showingcomponent 614 “any” because user interface 102 and/or pronunciationguesser 202 may not consider component 614 to be sufficiently relevantto component 604 “bell” and/or component 606 “ya.”

In some configurations, any one or more rows or columns of thecomponents 604-626 may be displayed via display 600. For example, afirst column including components 604, 610, 616, and 622 may beinitially displayed. Once a user selects one of the components of thefirst column, a second column including components 606, 612, 618, and624 may be displayed. The first column may be removed from display 600.Once a user selects a component of the second column, a third columnincluding components 608, 614, 620, and 626 may be displayed while thecomponents of second column may be removed from display 600. Additionalcolumns of mono-syllabic components may be presented in a similar mannerand so on.

User interface 102 may use a similar approach for the display of rowssuch as, for example, a row including components 604, 606, and 608.Other portions and/or groups of mono-syllabic components may bedisplayed dynamically based on the selection of one or more othermono-syllabic components. In some configurations, user interface 102 viadisplay 600 provides one or more mono-syllabic entry fields 622, 624,and 626 to receive user inputted mono-syllabic components and/or words.In on implementation, the user interface 102 stores the user-inputtedmono-syllabic components in a data store such as data store 106 and/ordata store 312 for subsequent user by user interface 102 by the userand/or for subsequent use by other users associated with other userdevices such as user devices 304 and 306.

FIG. 7 is a display 700 of yet another name 702 “Hafsteinsson” includingits monosyllabic components 704-720. The user interface 102 via display700 may provide features as discussed above with respect to displays 500and 600. In some implementations, the user interface 102 via display 700provides a list including one or more constructed phoneticpronunciations of a name to a user for selection. Instead of, forexample, providing a set of user selectable mono-syllabic components704, 706, and 708, the user interface 102 provides the constructphonetic pronunciation including the components 704, 706, and 708 as“yaf-stein-son.”

Likewise, the user interface 102 via display 700 provides otherconstructed phonetic pronunciations such as “Half-steen-sown” based oncomponents 710, 712, and 714, and so on. Element 414 provides anillustration of a display of multiple pronunciations for the name“Hafs.”Thus, user interface 102 via displays 500, 600, or 700 mayprovide a list of ways in which a name can be pronounced includingvarious combinations of mono-syllabic components. The user interface 102via display 700 may provide one or more mono-syllabic entry fields 716,718, and 720 to receive user inputted mono-syllabic components and/orwords.

Returning to FIG. 4, once a name pronunciation selection and/or guess iscompleted in Step 406, whether by using constrained recognition toautomatically recognize and select the closest available guess or byusing user interface 102 to provide a user with a display of selectablemono-syllabic components to construct a phonetic pronunciation of aname, synthesizer 206 receives and synthesizes the selectedmono-syllabic components to generate and/or construct a phoneticpronunciation of the name (Step 408). The constructed phoneticpronunciation of the name may be in the form of electronic data such asan audio file. In one configuration, the synthesizer 202 provides thephonetic pronunciation to user interface 102 for audio presentationand/or playback to a user via, for example, one or more speakers of userinterface 102.

A user, in response to hearing the pronounced name may accept or rejectthe constructed phonetic pronunciation (Step 410). For example, the userinterface 102 may receive a user input “yes” to accept the presentedphonetic pronunciation of a name or receive a user input “no” to rejectthe presented phonetic pronunciation of a name. The user input may beprovided via a user input device such as a touch screen, mouse, keypad,and/or audio input.

If the user accepts the phonetic pronunciation, then the user-drivenpronunciation system such as system 100 and/or 300 stores the userselected phonetic pronunciation for a name in, for example, data store106 and/or 312 for subsequent use and/or playback to the user (Step412). If the user rejects the phonetic pronunciation associated with thename, the user-driven pronunciation system 100 and/or 300 returns toStep 406 of process 400 to determine the next available closest guess orto allow the user to select a new arrangement of mono-syllabiccomponents for a name. Thus, in certain implementations, Steps 406through 410 may be performed iteratively until a user is satisfied witha particular phonetic pronunciation of a name.

Generally, the systems and methods herein enable user-driven namepronunciation. Various techniques allow for a user to say a name thatcan be recognized and synthesized into a more accurate and properpronunciation of the name by an electronic device. The techniques alsoenable a device to provide a user with a list of ways that a name can bepronounced so that the user can select a more accurate pronunciation.Furthermore, the systems and methods herein provide a user interfacethat enables a user to select one or mapped mono-syllabic componentsassociated with a name to construct a more accurate pronunciation of thename by an electronic device.

FIG. 8 is a diagram of a system 800 for determining phoneticpronunciations of a name. The system 800 includes a pronunciationguesser 802, phonetic mapper 804, and constrained recognizer 806. Thepronunciation guesser 802 also includes multiple pronunciation guessers808, 810, and 812. Each of the pronunciation guessers is associated witha particular language and/or locale. For example, guesser 808 may beassociated with the French language and utilize a French phoneticalphabet to guess pronunciations. Guesser 810 may be associated with theGerman language and utilize a German phonetic alphabet to guesspronunciations. Guesser 812, for example, may be associated with theEnglish language and utilize an English phonetic alphabet to guesspronunciations.

In certain implementations, the pronunciation guesser 802 includespronunciation guesser 202 of FIG. 2. The constrained recognizer 806 mayinclude the recognizer 204 of FIG. 2. Also, the phonetic mapper 804 maybe included in any one or more of the components 202-210 of FIG. 2.Furthermore, any one of the functions and/or operations of thecomponents 802-812 may be implemented by one or more processors such as,for example, processor 104 of FIG. 1.

In certain implementations, a user via interface 102 may speak and/orprovide an audio representation (e.g., recording) of a name that ispronounced in a certain way. The interface 102 may receive a name andrecording of how the user chooses to pronounce the name. The interface102 may receive a text entry for the name which is passed through theone or more guessers 808, 810, and 812. The recording of how topronounce the name may then be recognized from a constrained list ofpronunciations guessed from the one or more guessers 808, 810, and 812and/or locales (after phonetic mapping to a target locale). The system800 may then recognize the pronunciation that best matches how the usersaid the name.

More particularly, the constrained recognizer 806 may select the bestmatch and/or a match that is substantially close to the spoken and/orprovided name. A constrained list of pronunciation guesses may begenerated by multiple pronunciation guessers 808, 810, and 812. WhileFIG. 8 shows three guessers, the number of guessers may vary from one toany number of guessers that can be efficiently supported by the system800.

In certain implementations, a name is passed through multiple guessers808, 810, and 812 that support the character set of a particularlanguage or locale (for example, an English name may not be representedwell in a Japanese locale, but will be represented better in a Frenchlocale). The pronunciation guess from each pronunciation guesser 810 and812 associated with a different language and/or locale is then mapped bymapper 804 to the phonetic alphabet of a target locale such as, forexample, the phonetic alphabet associated with pronunciation guesser808. This mapping algorithm and/or process is done by mapper 804 unitthat maps the sound units and/or phonemes from the phonetic alphabet ofeach guesser 810 and 812 to the phonetic alphabet of the target guesser808 and its associated phonetic alphabet. The mapper 804 may map variousphonetic components such as, without limitation, sound units, phonemes,mono-syllabic components, syllabic components with types of stresses,portions of words, and the like. Constrained recognizer 806 may thenperform a constrained recognition to select the best match from theseover-generated pronunciations.

In an additional aspect, name pronunciations are used for recognition aswell as speech synthesis by, for example, synthesizer 206. In the caseof speech synthesis, the phonetic alphabet to be mapped to may bedifferent from the recognition alphabet. For speech synthesis, thephonetic alphabet is the one supported by the speech synthesizer used torender the spoken pronunciation. In one configuration, the synthesizer206 and/or any one of the other components of FIG. 2 guesses thesyllable stress when synthesizing a name based on a speech synthesisdictionary. The syllable stress may be derived from a set of rules thatare specific to a language and/or locale. For example, the name “Obama”includes sound units “o”, “bam”, and “a.” The first sound unit “o” maybe stressed such that the name is pronounced “Ohh-bam-a.” Alternatively,the last unit of the name may be stressed such that the name ispronounced “O-bam-Ahh.” In certain configurations, the system 800 and/or100 includes various sounds units that are stressed or not stressed. Thevarious sound units may be presented to a user as alternative selectablecomponents like, for example, the components illustrated in FIGS. 5-7.In some implementations, the system 800 may present variouspronunciations to a user including pronunciations with stressed andunstressed sound units which a user may select.

In an further aspect, a processor such as processor 104 may constrainthe number and/or list of guessers 808, 810, and/or 812 to pass a namethrough by using a language identification process and/or function thatprunes and/or reduces the number of guessers 808, 810, and/or 812. Thelanguage identification process and/or function may rank and/or providea score that estimates the languages and/or locales that best fit aname. The processor 104 can then prune and/or reduce the list ofguessers to constrain the number of guessers. This may be advantageouswhere the system 800 and/or 100 has limited capabilities (e.g.,processing power, memory, and other resources) to enable the system 800and/or 100 to more rapidly and efficiently provide name pronunciationsto a user.

FIG. 9 is a flow diagram of a process 900 for generating a phoneticpronunciation of a name. A system such as system 800 may include and/orbe provided with a plurality of pronunciation guessers 808, 810, and/or812 where each of the pronunciation guessers 808, 810, and/or 812 areassociated with a particular phonetic alphabet of a language or locale(Step 902). A processor such as processor 104 determines a language orlocale associated with a user (Step 904) and associates a first phoneticalphabet with the language or locale associated with the user (Step906). The determination of language and/or locale may be viamanufacturer input, service provider input, user input, detection of thegeographic area associated with the location of the system 800 and/or100, analysis of the types of names and/or other words input by a user,and the like.

Each of the pronunciation guessers 808, 810, and/or 812 receives arepresentation of the name (Step 908). The representation may beorthographic. Each of the plurality of pronunciation guessers 808, 810,and/or 812 guess a phonetic pronunciation of one or more components ofthe name (Step 910). Then, a phonetic mapper 804 maps the phoneticpronunciation of the one or more components of the name guessed by eachof the plurality of pronunciation guessers 808, 810 and 812 to the firstphonetic alphabet to generate to generate a list of guessedpronunciations (Step 912). In certain configurations, mapper 804 and/orprocessor 104 may receive a phonetic pronunciation that is transcribedby a linguist in a lexicon associated with the first phonetic alphabetand/or another phonetic alphabet, which may be included in the list ofguessed pronunciations. A recognizer such as recognizer 806 may receivean audio pronunciation of the name (Step 914) and then select acombination of components from the list of guessed pronunciations that,when pronounced, substantially and/or best match the audio pronunciationof the name (Step 916).

Each of the one or more components of the name may include at least oneof a sound unit, a phoneme, a mono-syllabic component, a mono-syllabiccomponent with a particular type of stress, and portion of a word. Theprocessor 102 may identify the language or locale associated with theuser. The number of pronunciation guessers 808, 810, and/or 812 may bedetermined based on the language or locale associated with the user. Thetype of each of the plurality of pronunciation guessers 808, 810, and/or812 may be determined based on the language or locale associated withthe user. The type of pronunciation guesser may include the type oflanguage or locale associated with the pronunciation guesser.

FIG. 10 is a flow diagram of another process 1000 for generating aphonetic pronunciation of a name based on user selection of the name'smonosyllabic components. A system such as system 100 of FIG. 1 mayassociate a phonetic pronunciation with a name. The system 100 mayinclude a user interface 102 arranged to receive the name (Step 1002).The system may also include a processor 104 arranged to map the name toa plurality of monosyllabic components that are combinable to constructthe phonetic pronunciation of the name (Step 1004). The user interface102 may also be arranged to receive a user input to select one or moreof the plurality of monosyllabic components (Step 1006). Furthermore,the processor 104 may be arranged to combine the selected one or more ofthe plurality of monosyllabic components to construct the phoneticpronunciation of the name (Step 1008).

In one configuration, the user interface 102 is arranged to provide thephonetic pronunciation to the user. The user interface 102 may bearranged to receive a second user input to select or reject the phoneticpronunciation. The user interface 102 may also be arranged to display afirst portion of the plurality of monosyllabic components to the user.The user interface 102 may further be arranged to display a secondportion of the monosyllabic components in response to a user selectionof one of the first portion of the plurality of monosyllabic components.

The processor 104 may be arranged to receive the name from a contactlist of a contact application 208 and/or other application 210associated with the user. The name may be in text format. The processor104 may be arranged to query a data store 106 and 312 that includes oneor more of the monosyllabic components associated with the name. Themonosyllabic components may include components associated with one ormore language and/or locales. The construction of the phoneticpronunciation of the name may include generating an audio file.

FIG. 11 is a flow diagram of a process 900 for determining usageinformation associated with the phonetic pronunciation of a name. Asystem for determining usage of phonetic pronunciations of a name suchas system 300 of FIG. 3 may include a server 310 arranged to receive thename (Step 1102). The system 300 may include a data store 312 arrangedto store one or more phonetic pronunciations associated with the name(Step 1104). The server 310 may be arranged to receive an indication ofthe one or more phonetic pronunciations associated with the name fromone or more user devices 302, 304, and 306 (Step 1106) and determineusage data associated with the one or more phonetic pronunciationsassociated with the name (Step 1108).

The indication may include the one or more phonetic pronunciations. Theindication may include a selection of the one or more phoneticpronunciations from the one or more user devices 302, 304, and 306. Theusage data may include an amount of instances that the indication isreceived during a period of time. The server 310 may be arranged toprovide at least one of the phonetic pronunciations associated with thename to a first user device 302 based on the usage data.

It will be apparent to those of ordinary skill in the art that thesystems and methods involved in the present application may be embodiedin a computer program product that includes a computer usable,non-transitory, and/or readable medium. For example, such a computerusable medium may consist of a read only memory device, such as a CD ROMdisk or conventional ROM devices, or a random access memory, such as ahard drive device or a computer diskette, or flash memory device havinga computer readable program code stored thereon.

It is understood that the various features, elements, or processes ofthe foregoing figures and description are interchangeable or combinableto realize or practice the implementations describe herein. Thoseskilled in the art will appreciate that aspects of the application canbe practiced by other than the described implementations, which arepresented for purposes of illustration rather than of limitation, andthe aspects are limited only by the claims which follow.

What is claimed is:
 1. A method comprising: receiving a name; mappingthe name to a plurality of monosyllabic components that are combinableto construct a phonetic pronunciation of the name; receiving a userinput to select one or more of the plurality of monosyllabic components;and combining the selected one or more of the plurality of monosyllabiccomponents to construct the phonetic pronunciation of the name.
 2. Themethod of claim 1 comprising outputting the phonetic pronunciation via auser interface.
 3. The method of claim 2 comprising receiving a seconduser input to select or reject the phonetic pronunciation.
 4. The methodof claim 1 comprising displaying a first portion of the plurality ofmonosyllabic components via a user interface.
 5. The method of claim 4comprising displaying a second portion of the monosyllabic components inresponse to a user selection of one of the first portion of theplurality of monosyllabic components.
 6. The method of claim 1comprising receiving the name from a user associated contact list. 7.The method of claim 6, wherein the name includes at least one of a firstname and last name.
 8. The method of claim 1 comprising querying a datastore that includes one or more of the monosyllabic componentsassociated with the name.
 9. The method of claim 1, wherein themonosyllabic components include components associated with one or morelanguages or locales.
 10. The method of claim 1, wherein constructingthe phonetic pronunciation of the name includes generating an audiofile.
 11. A system comprising: a user interface arranged to receive thename; a processor arranged to map the name to a plurality ofmonosyllabic components that are combinable to construct the phoneticpronunciation of the name; the user interface arranged to receive a userinput to select one or more of the plurality of monosyllabic components;and the processor arranged to combine the selected one or more of theplurality of monosyllabic components to construct the phoneticpronunciation of the name.
 12. The system of claim 11, wherein the userinterface is arranged to provide the phonetic pronunciation.
 13. Thesystem of claim 12, wherein the user interface is arranged to receive asecond user input to select or reject the phonetic pronunciation. 14.The system of claim 11, wherein the user interface is arranged todisplay a first portion of the plurality of monosyllabic components. 15.The system of claim 14, wherein the user interface is arranged todisplay a second portion of the monosyllabic components in response to auser selection of one of the first portion of the plurality ofmonosyllabic components.
 16. The system of claim 11 wherein theprocessor is arranged to receive the name from a user associated contactlist.
 17. The system of claim 16, wherein the name is in text format.18. The system of claim 11 comprising a data store, wherein theprocessor is arranged to query the data store that includes one or moreof the monosyllabic components associated with the name.
 19. The systemof claim 11, wherein the monosyllabic components include componentsassociated with one or more languages orlocales.
 20. The system of claim11, wherein constructing the phonetic pronunciation of the name includesgenerating an audio file.
 21. A method comprising: providing a pluralityof pronunciation guessers, each of the plurality of pronunciationguessers being associated with a phonetic alphabet of a language orlocale; determining a user language or a user locale; associating afirst phonetic alphabet with the user language or the user locale;receiving at each pronunciation guesser a representation of the name;guessing, at each pronunciation guesser, a phonetic pronunciation of oneor more components of the name; mapping the phonetic pronunciation ofthe one or more components of the name guessed by each of the pluralityof pronunciation guessers to the first phonetic alphabet to generate alist of guessed pronunciations; receiving an audio pronunciation of thename; and selecting a combination of components from the list of guessedpronunciations that, when pronounced, substantially matches the audiopronunciation of the name.
 22. The method of claim 21, wherein the oneor more components of the name include at least one of a sound unit, aphoneme, a mono-syllabic component, a mono-syllabic component with aparticular type of stress, and portion of a word.
 23. The method ofclaim 21 comprising receiving an input identifying the user language oruser locale.
 24. The method of claim 23, wherein at least one of theplurality of pronunciation guessers and the type of each of theplurality of pronunciation guessers is determined based on the userlanguage or the user locale.
 25. The method of claim 21, wherein thetype of pronunciation guesser includes the type of language or localeassociated with the pronunciation guesser.
 26. A system for determiningthe pronunciation of a name comprising: a plurality of pronunciationguessers, each of the plurality of pronunciation guessers beingassociated with a phonetic alphabet of a language or locale, each of theplurality of pronunciation guessers arranged to receive a representationof the name; a processor arranged to determine a language or localeassociated with a user and associate a first phonetic alphabet with thelanguage or locale associated with the user; each of the plurality ofpronunciation guessers arranged to guess a phonetic pronunciation of oneor more components of the name; a phonetic mapper arranged to map thephonetic pronunciation of the one or more components of the name guessedby each of the plurality of pronunciation guessers to the first phoneticalphabet to generate a list of guessed pronunciations; and a recognizerarranged to receive an audio pronunciation of the name and select acombination of components from the list of guessed pronunciations that,when pronounced, substantially matches the audio pronunciation of thename.
 27. The system of claim 26, wherein the one or more components ofthe name include at least one of a sound unit, a phoneme, amono-syllabic component, a mono-syllabic component with a particulartype of stress, and portion of a word.
 28. The system of claim 26,wherein the processor identifies the language or locale associated withthe user.
 29. The system of claim 28, wherein at least one of theplurality of pronunciation guessers and the type of each of theplurality of pronunciation guessers is determined based on the languageor locale associated with the user.
 30. The system of claim 26, whereinthe type of pronunciation guesser includes the type of language orlocale associated with the pronunciation guesser.
 31. A method fordetermining usage of phonetic pronunciations of a name comprising:receiving the name; storing one or more phonetic pronunciationsassociated with the name; receiving an indication of the one or morephonetic pronunciations associated with the name from one or more userdevices; and determining usage data associated with the one or morephonetic pronunciations associated with the name.
 32. The method ofclaim 31, wherein the indication includes the one or more phoneticpronunciations.
 33. The method of claim 31, wherein the indicationincludes a selection of the one or more phonetic pronunciations from theone or more user devices.
 34. The method of claim 31, wherein the usagedata includes an amount of instances that the indication is receivedduring a period of time.
 35. The method of claim 31 comprising providingat least one of the phonetic pronunciations associated with the name toa first user device based on the usage data.
 36. A system fordetermining usage of phonetic pronunciations of a name comprising: aserver arranged to receive the name; a data store arranged to store oneor more phonetic pronunciations associated with the name; and whereinthe server is arranged to receive an indication of the one or morephonetic pronunciations associated with the name from one or more userdevices and determine usage data associated with the one or morephonetic pronunciations associated with the name.
 37. The system ofclaim 36, wherein the indication includes the one or more phoneticpronunciations.
 38. The system of claim 36, wherein the indicationincludes a selection of the one or more phonetic pronunciations from theone or more user devices.
 39. The system of claim 36, wherein the usagedata includes an amount of instances that the indication is receivedduring a period of time.
 40. The system of claim 36, wherein the serveris arranged to provide at least one of the phonetic pronunciationsassociated with the name to a first user device based on the usage data.